View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000538 | T99X171.00 SKB Eagle | SW | public | 2019-03-06 11:19 | 2019-03-15 09:37 |
| Reporter | (ALTech) Jewoo Lee | Assigned To | (ALTech) Jewoo Lee | Due Date | |
| Priority | high | Severity | s3-moderate | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Summary | 0000538: How to get valid logs in Aging test | ||||
| Description | ALT is trying to setup Aging test of STB now. The test criteria from SKB is that there is no problem in aging test for 72 hours. So we need the way to get logs during overall test period(at least 72 hours) to debug the issues like lag, freezing(halt), reset(reboot), and so on. Please provide the information for this. | ||||
| Tags | No tags attached. | ||||
| Attach Tags | |||||
| related to | 0000536 | closed | ADB Bugreport extraction failure |
|
|
There are 2 way to capture system log. Case 1: You can use terminal (console) to capture by command logcat (type logcat in console) Case 2: You can use adb in windows cmd or linux terminal adb connect x.x.x.x (x.x.x.x means box's ip) adb logcat |
|
|
Hi Jason, Thanks for information. Could you give your answer my extra questions below? 1) Is it possible to get all logs for 72 hours by logcat? 2) Is there a way to save this log to USB storage? (We have to test over 15 devices at the same time.) 3) According to future plan, the SW will be built only as user and SELinux enforcing mode. In this case, is there a way to get valid logs? |
|
|
Hi Jweoo, 1) We haven't capture logcat for long time testing. I think if the adb connection is connected, you can capture it for long time. About the log file size, we get 161MB file size for capturing 5 mins, but we think the logcat size may different according different test case 2, 3) Do you want to save log to usb disk on OTT box? You can use logcat command in user mode, but you can not save the log to usb disk on OTT box due to security policy. For security restrictions, I suggested that you can capture device logs on Host (PC) side On Host (PC) side, adb connect device1's IP adb connect device2's IP adb connect device3's IP .... adb -s device1's IP logcat > device1_log.txt adb -s device2's IP logcat > device2_log.txt adb -s device3's IP logcat > device3_log.txt |
|
|
Hi Jason, Thanks for your help. I am worried that the log file won't be properly handled due to large size of logs when I see your comment(161MB for 5mins). Could you additionally advise about the way to continuously save the log with the specific size or time unit? |
|
|
Hi Jweoo, We don't have any tool to specific size or time unit. You can use logcat -s tag1 tag2 to reserve the tag you want to see. I think this way can help you to reduce the file size. For example: tag1 is chromium, tag2 is Finsky cts@cts-Veriton-M490:~/Downloads/$ adb logcat -s chromium Finsky > log.txt You can see only these 2 log in logfile log.txt --------- beginning of system --------- beginning of crash --------- beginning of main 03-07 16:47:03.121 4545 4545 I Finsky : [2] com.google.android.finsky.scheduler.JobSchedulerEngine.a(103): Cancelling existing job with id: 9001 03-07 16:47:03.125 4545 4545 I Finsky : [2] com.google.android.finsky.scheduler.JobSchedulerEngine.a(93): Scheduling job Id: 9000, L: 14948, D: 86399948, C: false, I: false, N: 1 03-07 16:47:46.853 4667 4667 I chromium: [4667:4667:INFO:metrics_recorder.cc(89)] Metrics stat: total=3 03-07 16:47:46.853 4667 4667 I chromium: Cast.Discovery.Mdns.Query.Cast.Count=1 03-07 16:47:46.853 4667 4667 I chromium: Cast.Discovery.Mdns.Request.In=1 03-07 16:47:46.853 4667 4667 I chromium: Cast.Discovery.Mdns.Response.Out=1 |
|
|
Hi Jason, We're considering to save the logcat and kernel logs to USB storage. Please check if this functionality is supported in the current F/W version and let us know how to get/run them. |
|
|
Hi Eric, If you want to save log into usb storage on OTT, You can use following commands to save logcat or kernel logs (On Box's terminal: adb shell or console) #su #logcat > /storage/xxx (logcat, xxx means usb name) #cat /proc/kmsg > /storage/xxx (kernel msg, xxx means usb name) Current F/W is "userdebug" build, so you use "su" command to change your permission then capture kmsg/logcat and redirect the logs to usb storage on OTT. |
|
|
Hi Jason, Thanks for your information. In case of kernel logs, it doesn't seem that the kernel log continue to save, so the saved log's size is very small. We want to continue to save the kernel log in real time via any command just like adb logcat's log. We would be grateful if you could provide us with the way. |
|
|
Hi Eric, Currently, we don't have any way to capture kernel log continuely into usb drive. I think you can use uart interface and terminal application to monitor kernel log. You can also refer mantis 539 to get kernel crash log https://mantis.cnsbg.foxconn.com/vaas/view.php?id=539 |
|
|
Hi Jason, We're planning to do the aging test for 72 hours in accordance with SKBB's criteria. As you know, we will not be able to UART interface on each device since many devices would be used for the aging test. If you need a kernel log for debugging any issue(except for kernel panic), how can we provide you with the relevant log without continuing to gather for 72 hours? Please advise it. |
|
|
Hi Eric, I found the option (-w) of dmesg for capturing kernel log continuely. dmesg -w > /storage/xxx |
|
|
Hi Jason, Thanks for your valuable information. |
|
|
Hi Jewoo, Please check if this case can be closed. |
|
|
Confirmed the way to get the valid logs for Aging test. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2019-03-06 11:19 | (ALTech) Jewoo Lee | New Issue | |
| 2019-03-06 11:19 | (ALTech) Jewoo Lee | Status | new => assigned |
| 2019-03-06 11:19 | (ALTech) Jewoo Lee | Assigned To | => (SW) Jacky Chiang |
| 2019-03-06 16:46 | (SW) Jacky Chiang | Assigned To | (SW) Jacky Chiang => (SW) Jason Ling |
| 2019-03-06 16:52 | (SW) Jacky Chiang | Relationship added | related to 0000536 |
| 2019-03-06 17:03 |
|
Note Added: 0001358 | |
| 2019-03-06 17:03 |
|
Assigned To | (SW) Jason Ling => (ALTech) Jewoo Lee |
| 2019-03-06 18:22 | (ALTech) Jewoo Lee | Note Added: 0001365 | |
| 2019-03-06 18:23 | (ALTech) Jewoo Lee | Assigned To | (ALTech) Jewoo Lee => (SW) Jason Ling |
| 2019-03-07 09:10 |
|
Assigned To | (SW) Jason Ling => (ALTech) Jewoo Lee |
| 2019-03-07 09:10 |
|
Note Added: 0001382 | |
| 2019-03-07 09:56 | (ALTech) Jewoo Lee | Note Added: 0001383 | |
| 2019-03-07 09:56 | (ALTech) Jewoo Lee | Assigned To | (ALTech) Jewoo Lee => (SW) Jason Ling |
| 2019-03-07 17:02 |
|
Assigned To | (SW) Jason Ling => (ALTech) Jewoo Lee |
| 2019-03-07 17:02 |
|
Note Added: 0001402 | |
| 2019-03-08 19:23 |
|
Note Added: 0001425 | |
| 2019-03-11 09:38 |
|
Note Added: 0001432 | |
| 2019-03-11 11:37 |
|
Note Added: 0001434 | |
| 2019-03-12 10:20 | (SW) Kerwin Chen | Severity | s2-severe => s3-moderate |
| 2019-03-12 20:25 |
|
Note Added: 0001469 | |
| 2019-03-13 10:57 |
|
Note Added: 0001487 | |
| 2019-03-14 13:24 |
|
Assigned To | (ALTech) Jewoo Lee => (SW) Jason Ling |
| 2019-03-14 15:15 |
|
Assigned To | (SW) Jason Ling => (ALTech) Eric Kim |
| 2019-03-14 15:15 |
|
Note Added: 0001522 | |
| 2019-03-14 16:30 |
|
Note Added: 0001524 | |
| 2019-03-14 16:42 |
|
Note Added: 0001525 | |
| 2019-03-14 16:42 |
|
Assigned To | (ALTech) Eric Kim => (ALTech) Jewoo Lee |
| 2019-03-15 09:37 | (ALTech) Jewoo Lee | Status | assigned => closed |
| 2019-03-15 09:37 | (ALTech) Jewoo Lee | Resolution | open => fixed |
| 2019-03-15 09:37 | (ALTech) Jewoo Lee | Note Added: 0001532 |
